home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19950726-19950929
/
000244_news@columbia.edu_Tue Aug 29 12:53:37 1995.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
3KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA25287
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Tue, 29 Aug 1995 08:53:43 -0400
Received: by apakabar.cc.columbia.edu id AA13444
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Tue, 29 Aug 1995 08:53:42 -0400
Path: news.columbia.edu!watsun.cc.columbia.edu!fdc
From: fdc@watsun.cc.columbia.edu (Frank da Cruz)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Kermit Waiting ...
Date: 29 Aug 1995 12:53:37 GMT
Organization: Columbia University
Lines: 52
Message-Id: <41v2kh$d42@apakabar.cc.columbia.edu>
References: <41ur8a$4ns@news.Ieunet.ie>
Nntp-Posting-Host: watsun.cc.columbia.edu
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <41ur8a$4ns@news.Ieunet.ie>,
Eoin Bairead <ebairead@login.ieunet.ie> wrote:
: I've a Kermit .ini file on a PC (3.14) which automatically LOGS IN to a
: VAX, kicks of a (fairly) long job, and then GETs the job's output
: through a SERVER command on the VAX.
:
: The VAX job can take 1 minute (optimal) or 10 minutes (backup running)
:
: VAX KERMIT is kicked off in SERVER mode as soon as it finishes.
:
: My .INI commands are
: output \64LONGJOB\13 ; @LONGJOB
: input 9999 machine. ; get the "machine." prompts
: input 10 machine. ; from VAX KERMIT
: get OUTPUTFL.DAT ; get the VAX output
:
: what happens is that I get the File Transfer screen showing WHILE THE
: VAX JOB IS STILL RUNNING, and the File Transfer process falls over for
: retries.
:
: Am I doing something wrong.
:
You need to handle failures after each INPUT statement, for example:
INPUT 9999 machine
IF FAIL STOP 1 Failed - No Kermit server within 9999 seconds.
9999 seconds is 166 minutes, which should be more than ample time.
On the off-chance that some counter is overflowing, maybe you could get
by with a smaller number, like 1000, which would be 16 minutes.
More likely, however, something interfered with Kermit during the long
INPUT wait. Maybe you touched the keyboard, or maybe something is
messing with your PC's timer chip. You can add all sorts of debugging
capacity to your script to narrow down what is happening, for example:
ECHO Long INPUT begins at \v(time)
INPUT 1000 machine
IF FAIL STOP 1 Failed - No Kermit server at \v(time)
: LONGJOB.COM finishes up with
: $ KERMIT SERVER ! KERMIT is a symbol - $SYS$SYSTEM:KERMIT
:
I'd also recommend you convert from Kermit-32 to C-Kermit 5A(190).
Not only does it work better and faster, but it has a much more meaningful
message that you can look for:
KERMIT READY TO SERVE...
More info about current Kermit versions at http://www.columbia.edu/kermit/
- Frank